Skip to content

fix: restore current JS and Wasm GC emulator builds - #6

Merged
bobzhang merged 2 commits into
mainfrom
codex/moonbit-20261029-release
Oct 29, 2026
Merged

bobzhang merged 2 commits into
mainfrom
codex/moonbit-20261029-release

Conversation

@bobzhang

Copy link
Copy Markdown
Contributor

The current toolchain rejects the root JSON module manifest and the package's redundant UInt32 = UInt alias, since UInt32 is now a built-in type. Migrate the manifest and use the equivalent built-in type. Update browser asset paths from target to _build so the documented release builds can actually be loaded.

CI now exercises both JS and Wasm GC exports with the bundled nestest ROM and compares all 8,991 instruction addresses, CPU registers, and PPU/CPU cycle counters with the reference log. Both backends pass locally. Disassembly text is deliberately outside this state oracle: the emulator uses ISC rather than ISB spelling and has five pre-existing APU read-value differences near the end of the trace, already noted in its source. No reference trace or emulation implementation is changed.

This repairs the documented JS and Wasm GC targets only. Raw Wasm still fails on $moonbit.free; existing PR4's allocator change needs separate ownership validation and is left untouched. Eight existing deprecation warnings remain. No publication or claim of complete raw Wasm compatibility is included.

@bobzhang
bobzhang merged commit cd6d697 into main Oct 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant